In-person encounter system and method of use

ABSTRACT

A technological solution to the problem of meeting people solely through electronic communication is described. The technological solution includes receiving location data from a first user system a second user system of a potential encounter within a venue, and delivering a nudge from the first user system to the second user system. The nudge is a canned request to engage in an in-person communication for users associated with the first user system and the second user system. Upon confirmation of the nudge, and receiving confirmation of a human-to-human interaction, potential encounter contact information is provided to facilitate electronic communication between the first user system and the second user system.

INCORPORATION BY REFERENCE

The present patent application claims priority to the provisional patentapplication identified by U.S. Ser. No. 62/597,551, filed on Dec. 12,2017, the entire content of which is hereby expressly incorporatedherein by reference.

BACKGROUND

In this age of technology, people are increasingly using electronicdevice such as mobile phones and tablets “in-the-moment” to search forthings, find reviews, make purchases, and to make both social andprofessional connections. The trends for social connections areincreasingly becoming less planned and more serendipitous, due toinfluence from current application providers, such as Snapchat. Evenmore, social and dating spaces are moving towards immediate meetings.

Currently within the art, dating application and other personal meetingapplications typically running on smart phones connecting users using inapplication messaging systems. For example, Tinder is a dating app thatworks on proximity of the smart phones, but not specific location.Foursquare dating app has a feature that allows people to virtually“check in” to a specific place. HelloTel is another dating app thatallows people to check in to a specific location and then broadcast thatthey are interested in meeting up for drinks, dinner or networking.

Studies have shown, however, that users of dating apps tend tocommunicate solely through in application messaging systems within thedating apps and sometimes to the exclusion of any in personcommunications. Even further, in using a professional platform, such asLinkedIn, users feel that communications with other users trend towardsformal. As Whitney Wolfe, Founder of Bumble states, “ . . . oftentimes,success comes from spontaneous connections.”

As such, there is a need for a technological solution to the existingproblems involved in making an in-person encounter. Ideally, thetechnological solution would be able to sync users at a particularlocation to initiate in-person communications while respecting eachperson's rights to privacy. It is to such a technological solution thatconnects users in real-time, facilitates human-to-human interactions,while protecting and respecting the privacy of each user that thepresent disclosure is directed.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other objects and features of the present invention will bemore fully disclosed or rendered obvious by the following detaileddescription of the invention which is to be considered together with theaccompanying drawings wherein like numbers refer to like parts, andfurther wherein:

FIG. 1 illustrates a block diagram of an exemplary encounter system inaccordance with the present disclosure, configured to facilitate inperson communications between at least two users.

FIG. 2 illustrates a block diagram of an exemplary encounter softwareapplication for use in one or more user system of the encounter systemillustrated in FIG. 1.

FIGS. 3-9 illustrate exemplary screenshots provided by the encountersoftware application in accordance with the present disclosure.

FIG. 10 illustrates a block diagram of an exemplary encounter softwareapplication for use in one or more management systems of the encountersystem illustrated in FIG. 1.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Before explaining at least one embodiment of the presently disclosed andclaimed inventive concepts in detail, it is to be understood that thepresently disclosed and claimed inventive concepts are not limited intheir application to the details of construction, experiments, exemplarydata, and/or the arrangement of the components set forth in thefollowing description or illustrated in the drawings. The presentlydisclosed and claimed inventive concepts are capable of otherembodiments or of being practiced or carried out in various ways. Also,it is to be understood that the phraseology and terminology employedherein is for purpose of description and should not be regarded aslimiting.

In the following detailed description of embodiments of the inventiveconcepts, numerous specific details are set forth in order to provide amore thorough understanding of the inventive concepts. However, it willbe apparent to one of ordinary skill in the art that the inventiveconcepts within the disclosure may be practiced without these specificdetails. In other instances, certain well-known features may not bedescribed in detail in order to avoid unnecessarily complicating theinstant disclosure.

As used herein, the terms “comprises,” “comprising,” “includes,”“including,” “has,” “having,” or any other variation thereof, areintended to cover a non-exclusive inclusion. For example, a process,method, article, or apparatus that comprises a list of elements is notnecessarily limited to only those elements but may include otherelements not expressly listed or inherently present therein.

Unless expressly stated to the contrary, “or” refers to an inclusive orand not to an exclusive or. For example, a condition A or B is satisfiedby anyone of the following: A is true (or present) and B is false (ornot present), A is false (or not present) and B is true (or present),and both A and B are true (or present).

The term “and combinations thereof” as used herein refers to allpermutations or combinations of the listed items preceding the term. Forexample, “A, B, C, and combinations thereof” is intended to include atleast one of: A, B, C, AB, AC, BC, or ABC, and if order is important ina particular context, also BA, CA, CB, CBA, BCA, ACB, BAC, or CAB.Continuing with this example, expressly included are combinations thatcontain repeats of one or more item or term, such as BB, AAA, AAB, BBC,AAABCCCC, CBBAAA, CABABB, and so forth. A person of ordinary skill inthe art will understand that typically there is no limit on the numberof items or terms in any combination, unless otherwise apparent from thecontext.

In addition, use of the “a” or “an” are employed to describe elementsand components of the embodiments herein. This is done merely forconvenience and to give a general sense of the inventive concepts. Thisdescription should be read to include one or at least one and thesingular also includes the plural unless it is obvious that it is meantotherwise.

The use of the terms “at least one” and “one or more” will be understoodto include one as well as any quantity more than one, including but notlimited to each of, 2, 3, 4, 5, 10, 15, 20, 30, 40, 50, 100, and allintegers and fractions, if applicable, therebetween. The terms “at leastone” and “one or more” may extend up to 100 or 1000 or more, dependingon the term to which it is attached; in addition, the quantities of100/1000 are not to be considered limiting, as higher limits may alsoproduce satisfactory results.

Further, as used herein any reference to “one embodiment” or “anembodiment” means that a particular element, feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment. The appearances of the phrase “in oneembodiment” in various places in the specification are not necessarilyall referring to the same embodiment.

As used herein qualifiers such as “about,” “approximately,” and“substantially” are intended to signify that the item being qualified isnot limited to the exact value specified, but includes some slightvariations or deviations therefrom, caused by measuring error,manufacturing tolerances, stress exerted on various parts, wear andtear, and combinations thereof, for example.

Software may include one or more computer readable instructions thatwhen executed by one or more components cause the component to perform aspecified function. It should be understood that algorithms or processinstructions described herein may be stored on one or morenon-transitory computer readable medium. Exemplary non-transitorycomputer readable medium may include random access memory, read onlymemory, flash memory, and/or the like. Such non-transitory computerreadable mediums may be electrically based, optically based, and/or thelike.

Circuitry, as used herein, may be analog and/or digital components, orone or more suitably programmed processors (e.g., microprocessors) andassociated hardware and software, or hardwired logic. Also, “components”may perform one or more functions. The term “component,” may includehardware, such as a processor (e.g., microprocessor), an applicationspecific integrated circuit (ASIC), field programmable gate array(FPGA), a combination of hardware and software, and/or the like. Theterm “processor” as used herein means a single processor or multipleprocessors working independently or together to collectively perform atask.

Additionally, it is to further be understood that the provider andreceiver as described herein are not limited to human beings, and maycomprise, an animal, a thing, a computer, a server, a website, abusiness entity, a human, a group of humans, a virtual computer,combinations thereof, and the like, for example.

Certain exemplary embodiments of the invention will now be describedwith reference to the drawings. In general, such embodiments relate toconnection of at least two users in real-time, facilitating ahuman-to-human interaction between such users, while protecting privacyof each user.

Referring to the Figures, and in particular FIG. 1, shown therein is ablock diagram of an exemplary encounter system 10 to facilitate inperson meeting(s) between users. Generally, the encounter system 10 isdesigned and configured to overcome the problems associated with datingapps' drawbacks in facilitating human-human interaction between at leasttwo users (e.g., an in-person spontaneous conversation). For example,the encounter system 10 may notify a first user of one or more otherusers in close proximity, and facilitate one or more in-personcommunications (i.e., human-to-human interaction) at the exclusion of aninitial electronic communication (e.g., telephone conversation, e-mail,text) between users. In some embodiments, the encounter system 10 mayprovide one or more notifications that two or more mobile platforms arein close proximity at a particular location (e.g., a public space).Proximity may be determined in a number of ways including, but notlimited to, distance of the mobile platform to a particular location(e.g., restaurant, venue), distance between a first user and a seconduser, and/or the like. In some embodiments, the encounter system 10solely provides location of a user to other users only upon permissionof the user to provide such location. Notifications between users priorto human-to-human interaction may include, but are not limited to,personal data (e.g., name, image, date of birth), location data, and/orthe like. Notifications, however, do not include any means (e.g., phonenumber, email address, in-app messaging services) to facilitateelectronic conversations prior to an in person communication.

Generally, the encounter system 10 includes an encounter softwareapplication (e.g., mobile application) provided on a platform (e.g.,mobile platform). To facilitate a personal communication between twousers at a particular location, the encounter software application maypermit a first user to “nudge” a second user. A nudge may be defined asone or more signals transmitted from a first encounter softwareapplication to a second encounter software application indicative of acanned request from a first user to a second user to engage in an inperson communication (i.e., human-to-human interaction). The term“canned” as used herein refers to a prerecorded message lacking infreshness and spontaneity. If the second user does not want to beengaged by such interaction, the second user may reject the nudge bymanipulating the second encounter software application in a mannerindicating that the second user does not wish to be engaged in an inperson communication. If the second user does want to engage with thefirst user, then the second user accepts the nudge. Once a nudge isaccepted, the first user is aware that the second user is open tomeeting the first user in person thus facilitating a human-to-humaninteraction. In some embodiments, a nudge may only be provided whenusers are in the same geographic location (e.g., public venue).

The encounter system 10 may facilitate use of the encounter softwareapplication by the users by providing detailed location data. Locationdata may include, but is not limited to, specific venues of interest,virtual reality display indicating user location, and/or the like.

Referring to FIG. 1, the encounter system 10 may be a system or systemsthat are able to embody and/or execute the logic of the processesdescribed herein. Logic embodied in the form of software instructionsand/or firmware may be executed on appropriate hardware. For example,logic embodied in the form of software instructions or firmware may beexecuted on a dedicated system or systems, a distributed system, and/orthe like. In some embodiments, logic may be implemented in a stand-aloneenvironment operating on a single processor and/or logic may beimplemented in a networked environment, such as a distributed systemusing multiple computers and/or processors.

Referring to FIG. 1, the encounter system 10 includes a managementsystem 12. The management system 12 may include one or more processors14 configured to communicate with two or more user systems 16 over anetwork 18. The one or more processors 14 may work together, orindependently to execute processor executable code. Additionally, themanagement system 12 may include one or more memories 20 capable ofstoring processor executable code. In some embodiments, each element ofthe management system 12 may be partially or completely network-based orcloud-based, and may or may not be located in a single location.

The one or more processors 14 may be implemented as a single orplurality of processors working together, or independently, to executethe logic as described herein. Exemplary embodiments of the one or moreprocessors 14 may include, but are not limited to, a digital signalprocessor (DSP), a central processing unit (CPU), a field programmablegate array (FPGA), a microprocessor, a multi-core processor, and/orcombinations thereof, for example. The one or more processors may becapable of communicating via the network 18 or a separate network (e.g.,analog, digital, optical, and/or the like) via one or more ports (e.g.,physical or virtual ports) using a network protocol. The one or moreprocessors 14 may be capable of reading and/or executing processorexecutable code and/or capable of creating, manipulating, retrieving,altering, and/or storing data structure(s) into one or more memories(e.g., memory 20).

In some embodiments, at least a portion of the management system 12 maybe network-based, cloud based, and any variations thereof, and mayinclude the provision of configurable computational resources on demandvia interfacing with a computer and/or computer network, with softwareand/or data at least partially located on the computer and/or computernetwork, by pooling processing power of two or more networkedprocessors.

The management system 12 may read and/or execute processor executablecode and/or create, manipulate, retrieve, alter and/or store datastructures into one or more memories 20. The one or more memories 20 maystore processor executable code. Additionally, the one or more memories20 may be implemented as a conventional non-transitory memory, such as,for example, random access memory (RAM), a CD-ROM, a hard drive, a solidstate drive, a flash drive, a memory card, a DVD-ROM, a floppy disk, anoptical drive, combinations thereof, and/or the like, for example.

In some embodiments, the one or more memories 20 may be located in thesame physical location. Alternatively, one or more memories 20 may belocated in a different location as the management system 12 andcommunicating via a network, such as the network 18. Additionally, oneor more of the memories 20 may be implemented as a “cloud memory” (i.e.,one or more memories may be partially or completely based on or accessedusing a network, such as network 18, for example).

The one or more memories 20 may store processor executable code and/orinformation comprising one or more databases 22 and program logic 24. Insome embodiments, the processor executable code may be stored as a datastructure, such as a part of database and/or data table, for example. Insome embodiments, one of the databases 22 may be a user database storingidentifying characteristics retrieved and/or determined from one or moreusers for the encounter system 10. In some embodiments, one of thedatabases 22 may be a user communication database storing one or morecommunications received from the user system(s) 16 (e.g., nudges). Insome embodiments, one of the databases 22 may be a business affiliationdatabase storing one or more communication for transmission to one ormore user system(s) 16.

In some embodiments, the program logic 24 of the management system 12may include an application programming interfaces (API) 26 (e.g.,representational state transfer (Restful Service) API) to communicatewith the user system 16. It should be noted that the management system12 may communicate with the user system 16 via other methods including,but not limited to, simple object access protocol (SOAP), directcommunication, and/or the like.

The management system 12 may be capable of interfacing and/orcommunicating with the two or more user systems 16 via the network 18.The network 18 may be almost any type of network. For example, thenetwork 18 may interface by optical and/or electronic interfaces, and/ormay use a plurality of network topographies and/or protocols including,but not limited to, Ethernet, TCP/IP, circuit switched paths, and/orcombinations thereof. For example, in some embodiments, the network 18may be implemented as the World Wide Web (or Internet), a local areanetwork (LAN), a wide area network (WAN), a metropolitan network, awireless network, a cellular network, a Global System for MobileCommunications (GSM) network, a code division multiple access (CDMA)network, a 3G network, a 4G network, a satellite network, a radionetwork, an optical network, a cable network, a public switchedtelephone network, an Ethernet network, combinations thereof, and/or thelike. Additionally, the network 18 may use a variety of networkprotocols to permit bi-directional interface and/or communication ofdata and/or information. It is conceivable that in the near future,embodiments of the present disclosure may use more advanced networkingtopologies.

In some embodiments, the network 18 may be the Internet and/or othernetwork. For example, if the network 18 is the Internet, a primary userinterface of the user system 16 may be delivered through a series of webpages. It should be noted that the primary user interface of the usersystem 16 may be replaced by another type of interface, such as, forexample, a Windows-based application.

The user system 16 may be implemented as a smartphone, a tablet, alaptop computer, a personal computer, a desktop computer, a computerterminal, a computer workstation, an e-book reader, a wirelessnetwork-capable handheld device, a personal digital assistant, a kiosk,a gaming system, and/or the like. Similar to the management system 12,the user system 16 may be provided with one or more processors, one ormore non-transitory processor readable medium, an input device, and anoutput device. The processor, the one or more non-transitory processorreadable medium, the input device, and the output device of the usersystem 16 may be implemented similarly to or the same as the processor14.

The user system 16 may include one or more input devices 30, and one ormore output devices 32. The one or more input devices 30 may be capableof receiving information directly from a user, processor, and/orenvironment, and transmit such information to the one or more processors14 and/or the network 18. The one or more input devices 30 may include,but are not limited to, implementation as a keyboard, touchscreen,mouse, trackball, microphone, fingerprint reader, infrared port, cellphone, PDA, controller, network interface, speech recognition, gesturerecognition, eye tracking, brain-computer interface, combinationsthereof, and/or the like.

The one or more output devices 32 may be capable of outputtinginformation in a form perceivable by a user and/or processor(s). In someembodiments, the one or more output devices 32 may be configured tooutput information automatically (i.e., without human intervention). Forexample, in some embodiments, the one or more output devices 32 may becapable of printing or displaying at a pre-determined time interval alisting of users within a particular venue, a listing of nudges, alisting of connects, and/or the like. The one or more output devices 32may include, but are not limited to, implementation as a computermonitor, a screen, a touchscreen, a speaker, a website, a televisionset, an augmented reality system, a smart phone, a PDA, a cell phone, afax machine, a printer, a laptop computer, an optical head-mounteddisplay (OHMD), combinations thereof, and/or the like.

In some embodiments, the user system 16 may store processor executableinstructions or a software application. For example, the user system 16may include a web browser and/or a native software application runningon the user system 16 and configured to communicate with the managementsystem 12 over the network 18. The software application on the usersystem 16 may be configured to access a website and/or communicateinformation and/or data with the management system 12 over the network18.

FIG. 2 illustrates a flow chart 40 of an exemplary embodiment of anencounter software application for the encounter system 10 for use onthe user system 16 illustrated in FIG. 1. The encounter softwareapplication may be downloaded onto the one or more user systems 16 asshown in step 42. The encounter software application may provide alogin-page for the user on the user system 16.

The encounter software application may provide ability for storage andmanagement of a user account. To that end, a collection of dataassociated with a particular user of the encounter software applicationmay be stored in the management system 12 in the user account. In someembodiments, at least a portion of the data associated with a particularuser of the encounter software application may be stored on the usersystem 16 associated with the particular user. Each user account mayinclude, but is not limited to, user name, password, history ofinteractions with the encounter software application, settingpreferences, demographic data, and/or the like, for example.

In some embodiments, the encounter software application may providedifferent levels of access (e.g., premium access, basic access) to usersof the user systems 16. For example, a first user may be provided withpremium access providing additional features of use. To that end, theencounter software application may allow different levels of security orfunctionality based on compensation provided by the user.

The user may be given the option to create an account as in step 44 orsign-in to an already created account as in step 46. The user may begiven the option to enable location setting and/or enable notificationsvia the user system 16 as in step 48. Location settings of the usersystem 16 may allow the user system 16 to provide the geographiclocation of the user system 16 to the management system 12 for use inthe encounter software application as described in further detailherein. For example, in some embodiments, the user may allow themanagement system 12 access to location services of the user system 16.The user system 16 may relay positional data (e.g., GPS data) to themanagement system 12 via the API 26. The positional data may be recordedand/or stored in the one or more database 22 of the management system12. In some embodiments, the positional data of the user may be comparedto one or more public locations within proximity to the user.

During use of the encounter software application on the user system 16,the user may check-in to a location (e.g., a public location) as shownin step 50. For example, the user may be provided by the encountersoftware application a listing of locations within proximity to theuser. The user may select one or more locations from the listing oflocations within proximity to the user. As the user indicates via theuser system 16 that the user is checking-in to the location, the usersystem 16 may provide the geographic location of the user system 16 tothe encounter software application on the user system 16 and/or to themanagement system 12. The geographic location may be provided, forexample, by an internal GPS system within the user system 16. The userlocation may then be stored, for example, in one or more database 22 ofthe management system 12.

Referring to FIGS. 2 and 3, the encounter software application using theGPS location of the user system 16, may receive data indicative of alisting of other users at the same location as the user, and thenprovide the user with the listing of other users as shown in step 52.For example, in some embodiments, the user may check into one or morelocations creating a record within one or more database 22. Themanagement system 12 may also poll the API 26 and retrieve the user'spositional data. The management system 12 may then query the one or moredatabase 22 with the identification of position (e.g., locationidentification) and display one or more other users having one or morerecords within the one or more database 22 as being present at thatlocation. Such “other users” may herein be identified as “potentialencounters” for simplicity of description. For example, FIG. 3illustrates a screen shot 80 for a listing 82 of a first potentialencounter 84 and a second potential encounter 86 at a first venue 88.The first venue 88 is within a pre-determined geographic location asdetermined by the management system 12. In some embodiments, if nopotential encounters are present at the user's current location or at aprivate location provided by the user, then the encounter softwareapplication may present to the user one or more alternate locationshaving potential encounters present (e.g., a map illustrating one ormore locations having one or more potential encounters present) as shownin step 54.

In a step 56, the encounter software application may provide the userthe ability to view one or more profiles of the potential encounterspresent at the venue. For example, the encounter software applicationmay provide the user the ability to view the profile of the firstpotential encounter 84 and/or the second potential encounter 86. Viewingof the profile may be provided prior to any interaction with thepotential encounter. In some embodiments, the API 26 may retrieve one ormore records of users currently at a pre-defined location usingpositional data queries. User profiles of records determined to be atthe pre-defined location may be populated and/or displayed on the usersystem 16. Referring to FIG. 4, in some embodiments, the encountersoftware application may provide the user the ability to view partialprofiles (e.g., business title, blurred user image, first 100 charactersof user profile, and/or the like) of potential encounters within apre-determined vicinity of the user system 16. For example, FIG. 4illustrates a screen shot 90 wherein the encounter software applicationinforms the user that the user is within the vicinity (i.e., a fewblocks away) of the user system 16 of one or more potential encounters.Additionally, the encounter software application may provide one or morerecommendations to facilitate an in-person meeting. Such recommendationsmay include a particular venue, for example, at which the user andpotential encounters may be able to meet. Referring to FIG. 5, in someembodiments, the encounter software application may provide the user oneor more notifications when one or more potential encounters enter aparticular venue or within the vicinity of the user. For example, FIG. 5illustrates a screen shot 92 indicating that “2 new users just showed upat your location”.

In some embodiments, the encounter software application may include avirtual reality feature providing users one or more views of the venue.The one or more views of the venue may include one or more indicators ofone or more user systems 16 of potential encounters within apre-determined location. Such feature may be implemented in a crowdedvenue, for example.

In some embodiments, one or more venues and/or businesses may beaffiliated with the encounter software application. To that end,locations having high attendance (i.e., greater than a number ofpre-determined users present) may be highlighted (e.g. displayed) on theoutput device 32 to other users within the encounter softwareapplication (e.g., highlighted on a map). Highlighting may aid inpromoting the venue, businesses, and/or location to one or more users.In some embodiments, businesses may affiliate with the encountersoftware application and select one or more geographic regions toprovide users one or more notifications. For example, FIG. 6 is a screenshot 94 illustrating a business XYZ's affiliation with the encountersoftware application within a pre-determined geographic region. Withinthe pre-determined geographic region, the encounter software applicationprovides the notification to one or more user systems 16 to “Screenshotthis notification and come to XYZ tonight for $1 off your first beer.”

In some embodiments, the encounter software application may provide theuser an option of broadcasting the location of the user to potentialencounters. For example, a recruiter may be interested in filling aparticular position. The recruiter, as a user on the user system 16, mayselect the option to broadcast the recruiter's location at a particularvenue (e.g., coffee shop) on the output device 32 of user systems 16 topotential encounters. The encounter software application may provide theuser an additional option of including one or more notations related tosuch broadcast. For example, the recruiter may provide the notation “I'mlooking for a rock star copywriter. Bring your resume to ABC for a freecoffee and maybe a career change.” Potential encounters on users systems16 would be able to view the broadcast and decide whether to visit thevenue broadcasted.

In some embodiments, the encounter software application may providefiltering of users at particular venues. While providing anonymity ofusers at a venue, the encounter software application may providefiltering for one or more characteristics (job title, age, and/or thelike) of potential encounters. Users may then filter based on the one ormore characteristics. For example, FIG. 7 illustrates a screen shot 96provided by the encounter software application to the user system 16indicating that 1 CEO, 3 Designers and 1 Programmer are at a particularvenue. In some embodiments, the encounter software application mayprovide users the ability to sort profiles of potential encounters byinterests, tags, titles, and/or the like. In some embodiments, theencounter software application may provide the ability for the user viathe user system 16 to search and/or locate venues of interest for aparticular industry, job title, role, and/or the like. For example,searching for the title “CEO” may provide one or more trends of locationand time (e.g., what days, times and locations wherein users having aCEO title frequent).

In a step 58, the user may be able to block and/or report potentialencounters for conduct deemed inappropriate (e.g., language, threatingprofile, and/or the like). In a step 60, the user may be able toinitially interact with one or more potential encounters from thelisting of potential encounters at the venue 88. Initially interactionsmay be provided via a nudge. The nudge as defined herein is a request tothe first potential encounter 84 and/or the second potential encounter86 to engage in an in person communication with the user. If the firstpotential encounter 84 does not want to be engaged in an in personcommunication, the first potential encounter 84 may reject the nudge. Ifthe first potential encounter 84 does want to engage in an in-personcommunication, then the first potential encounter 84 may accept thenudge. Once a nudge is accepted, the user may be made aware that thefirst potential encounter 84 is open to meeting in person. In someembodiments, the encounter software application may limit nudges to apre-determined amount within a pre-determined time period. For example,nudges may be limited to 4 nudges within a 24 hour time period. In someembodiments, the limit on nudges may be dynamic and based upon type ofvenue, time of day, and/or the like, for example.

If the user and potential encounter meet in person, the interaction maybe deemed a “connect”. The “connect” is an in-person communicationbetween the user and the potential encounter. Following a connect, theencounter software application may provide the ability for the user andpotential encounter to share contact information (e.g., phone number,e-mail). In some embodiments, the encounter software application mayprompt the user to share contact information subsequent to the connect.In some embodiments, the encounter software application may provide oneor more icebreakers to the user and/or the potential encounter. Forexample, in some embodiments, if a first user would like to sharecontact information with a second user, the first user would indicate tothe management system 12 via the user system 16 that the first userwould like to connect. The second user may receive one or morenotifications (e.g., within the encounter software application, viae-mail, via text, and/or the like) with data that the first user wouldlike to share with the second user.

Icebreakers are notification to the user and potential encounter afterthe connect providing information and/or data relating to the user andpotential encounter. Such icebreaker notification may include, but arenot limited to, data related to social accounts, current events,geographic interest, shared interests, and/or the like. For example,FIG. 8 illustrates a screen shot 98 of an icebreaker provide to the usersubsequent to the connect. The icebreaker states, “Ask John about hisnew job!” John being the potential encounter. In some embodiments, theicebreakers may be provided using data from third party system (e.g.,LinkedIn). In some embodiments, subsequent to the connect between theusers, the user and potential encounter may score and/or rank thein-person interactions as shown in a screenshot 100 in FIG. 9. In someembodiments, the encounter software application may allow the user andpotential encounter to export contact information and/or data of eachother subsequent to the connect. In some embodiments, one or more thirdparties may sponsor notifications to each user.

Each user may be able to view one or more nudges and/or connects via theuser systems 16 as shown in step 62. Additionally, each user may be ableto respond to one or more nudges and/or connects via the user systems 16as shown in step 64. Subsequent to accepting a nudge from a potentialencounter or having a nudge accepted, the user may be able to connect inperson (i.e., a human to human interaction in real time) with thepotential encounter as shown in step 66.

Each user may be able to view their profile as shown in step 68.Additionally, each user may be able to edit their profile as shown instep 70. To that end, users may be able to upload images as shown instep 72. For example, the user may upload one or more profile images,video images, and/or the like. In some embodiments, the encountersoftware application may prompt users to upload a different profilepicture after a pre-determined amount of time or when arriving at aparticular location. For example, the encounter software application mayprompt a user to upload a new profile picture upon logging into theencounter software application. In some embodiments, the encountersoftware application may prompt a user to upload a new profile pictureupon arrival at a new location or after a pre-determined amount of timeat a particular location. In some embodiments, one additional feature ofuse may include the ability for the user to upload one or more shortvideos. The one or more short videos may be configured to be the user'smain profile picture in an animated format (e.g., animated GIF).

Each user may be able to view one or more settings within the encountersoftware application via the user systems 16 as shown in step 74. Suchsetting may include, but aren't limited to, notification settings,location settings, and/or the like. Each user may be able to edit theirsettings via the user systems 16 as shown in step 76. Additionally,users may be able to delete their user account and/or log-out of theencounter software application as shown in step 78.

FIG. 10 illustrates a flow chart 110 of the management system 12 of theencounter system 10. The management system 12 generally regulatesinteractions between two or more user systems 16.

In a step 112, the user using the user system 16 may sign into theencounter software application on the management system 12 via the API26. The management system 12 may create and/or store user accounts foreach user based on information and data provided by the user system 16via the API 26 as shown in steps 114 and 116. The encounter softwareapplication may receive GPS data from the user systems 16 as shown instep 118. In a step 120, the management system 12 may compare the GPSlocation of the user device 16 to locations within the database of themanagement system 12. In one example, the GPS location of the user maybe unidentifiable when comparing against the database of the managementsystem 12 as shown in step 122. In this scenario, the management system12 may poll the location of the user system 16 against the API 26. Ifthe location doesn't match, the management system 12 may assume that theuser is not at a public venue (e.g., the user is at home) as shown instep 126. To that end, the encounter software application may provide adisplay of public locations and/or users at public locations within thevicinity as shown in step 128. If the management system 12 determinesthe GPS location to be a valid public venue, the management system 12may store the new location within the database as shown in step 130.

Once the management system 12 determines the GPS location is within alocation capable of supporting the encounter software application (e.g.,public venue) as shown in step 132, the user may be provided the optionof checking into the location (e.g., sending a data signal from the usersystem 16 to the management system 12 indicating that the user desiresto check into the location) as shown in step 134. The management system12 may store the GPS location of the user systems 16 and/or duration ofstay at the GPS location as shown in step 136.

The management system 12 may then display user profiles of users at thevenue on the output device 32 of each user system 16 as shown in step136. The management system 12 may also display on each output device 32of the user system 16 the ability to nudge and/or connect with otherusers at the venue as shown in step 138. The management system 12provides the ability for users of the user system 16 to nudge potentialencounter (i.e., other users) at the venue as shown in step 140. Oncethe user nudges the potential encounter, the nudge may be displayed inthe encounter software application to each user related to the nudge fora pre-determined amount of time (e.g., 24 hours) as shown in step 142.Users may then connect in a human to human real time communication asshown in step 144. Additionally, the management system 12 may storenudges within the database as shown in step 146.

The encounter system and methods disclosed and claimed herein are welladapted to carry out the objects and to attain the advantages mentionedherein, as well as those inherent in the invention. The presentdisclosure provides a non-conventional, technical solution topre-existing problems of conventional dating applications. The problemwith conventional dating applications is that meeting other userselectronically has become a game. Users are able to interactelectronically with other users by swiping, gathering matches likeplaying cards, and rarely meeting the other user in person.Conventionally, if two users do decide to meet up, these users could becompletely different than what they portrayed themselves to be. With thepresently disclosed and non-conventional encounter software application,users are able to see if there are other users at different locations inclose proximity, e.g., across their city. But, the encounter softwareapplication does not allow the users to see who the other users areuntil the users are at the same location. Once users are at the samelocation, profiles (or partial profiles) may be available and such usersare able to initially interact via “nudges”. Nudges are different fromconventional electronic communication between two users for severalreasons. First, in some embodiments, nudges are only available when twousers are at the same location. Second, the nudge represents a simplecanned message, such as “hello, I'd like to visit with you.” Thepresently disclosed encounter software application does not allow directspontaneous messaging until after the users meet in person. Nudges takethe place of direct messaging and encourage two users to meet in personwhile the users are at the same location. In some embodiments, once auser leaves the location, such user can not receive a Nudge from a userstill at the location. In summary, the presently disclosed encountersoftware application solves the previous problems associated withspontaneous electronic communication between users of datingapplications, by facilitating real-time, location based, in personinteractions rather than digital messaging across vast distances.

While exemplary embodiments of the inventive concepts have beendescribed for purposes of this disclosure, it will be understood thatnumerous changes may be made which will readily suggest themselves tothose skilled in the art and which are accomplished within the spirit ofthe inventive concepts disclosed and claimed herein.

What is claimed is:
 1. One or more non-transitory computer readablemedium storing a set of computer executable instructions of an encountersoftware application for running on one or more processors that whenexecuted cause the one or more processors to facilitate an in-personcommunication between two users at an exclusion of an initialspontaneous electronic communication by: receiving location data for afirst user system, and a second user system, the first user systemhaving a first processor, a first non-transitory processor readablemedium, a first input device and a first output device, the second usersystem having a second processor, a second non-transitory processorreadable medium, a second input device, and a second output device, thefirst user system and the second user system being wirelessnetwork-capable mobile devices; determining if the first and second usersystems are within a pre-determined geographic area using the locationdata; providing a notification to the first user system of at least oneof personal data and location data of a user of the second user system,without any means to facilitate electronic conversations between thefirst user system and the second user system prior to the in-personcommunication; receiving a request from the first user system to send acanned request to the second user system, the canned request being oneor more signals indicative of a message lacking in freshness andspontaneity to engage in an in-person communication, the canned requestbeing configured to be accepted or rejected; displaying the message ofthe canned request on the second output device of the second usersystem; receiving acceptance of the canned request to engage in anin-person communication from the second user system; and requesting atleast one of the first user system, and the second user system to uploada different profile image when at least one or more of the followingoccurs: location data changes; after a pre-determined amount of time;when arriving at a particular location; a user of the first user systemlogging into the encounter software application, a user of the seconduser system logging into the encounter software application; uponarrival at a new location; or after a predetermined amount of time at aparticular location, the profile image being a picture or short video ofthe user.
 2. The one or more non-transitory computer readable mediumstoring a set of computer executable instructions for running on one ormore processors of claim 1, further comprising storing a user accountrelated to each user of each user system, the user account having aprofile image, the profile image being a picture or short video of theuser.
 3. The one or more non-transitory computer readable medium storinga set of computer executable instructions for running on one or moreprocessors of claim 1, further comprising requesting the first usersystem and the second user systems to upload a different profile imageat pre-determined intervals, the profile image being a picture or shortvideo of the user.
 4. The one or more non-transitory computer readablemedium storing a set of computer executable instructions for running onone or more processors of claim 3, wherein the pre-determined intervalsis a twenty-four hour period.
 5. The one or more non-transitory computerreadable medium storing a set of computer executable instructions forrunning on one or more processors of claim 1, further comprisingtransmitting to at least one of the first and second user systems atleast one notification indicating that the first and second user systemsare each in close proximity to a specific location.
 6. The one or morenon-transitory computer readable medium storing a set of computerexecutable instructions for running on one or more processors of claim1, further comprising providing a virtual reality display to at leastone of the first and second user systems, wherein the virtual realitydisplay identifies at least one of the first and second user systemwithin the pre-determined geographic area.
 7. The one or morenon-transitory computer readable medium storing a set of computerexecutable instructions for running on one or more processors of claim1, further comprising receiving a request from the first user system toview at least one of personal data and location data of the user of thesecond user system, the personal data including personal informationrelated to the user of the second user system, and excluding contactinformation.
 8. The one or more non-transitory computer readable mediumstoring a set of computer executable instructions for running on one ormore processors of claim 1, further comprising storing at least onecommunication of a business affiliation related to the pre-determinedgeographic area.
 9. The one or more non-transitory computer readablemedium storing a set of computer executable instructions for running onone or more processors of claim 1, further comprising receiving abroadcast and transmitting the broadcast to the first and second usersystems deemed within the pre-determined geographic area.
 10. The one ormore non-transitory computer readable medium storing a set of computerexecutable instructions for running on one or more processors of claim1, further comprising providing to the first user system at least onelist including the second user systems within the pre-determinedgeographic area and filtering the at least one list based on job titleof each user.
 11. The one or more non-transitory computer readablemedium storing a set of computer executable instructions for running onone or more processors of claim 1, further comprising providing at leastone icebreaker to at least one of the first and second user systemssubsequent to receiving confirmation of a connect, the icebreakerincluding personal data related to at least one user.
 12. The one ormore non-transitory computer readable medium storing a set of computerexecutable instructions for running on one or more processors of claim11, wherein the icebreaker includes data received from a third partysystem.
 13. An automated method performed by at least one processorrunning computer executable instructions of an encounter softwareapplication stored on at least one non-transitory computer readablemedium, comprising: receiving location data from a first user system anda second user system of a potential encounter, the first user system andthe second user system being wireless network-capable mobile devices;requesting at least one of the first user system, and the second usersystem to upload a different profile image when at least one or more ofthe following occurs: location data changes; after a pre-determinedamount of time; when arriving at a particular location; a user of thefirst user system logging into the encounter software application, auser of the second user system logging into the encounter softwareapplication; upon arrival at a new location; or after a predeterminedamount of time at a particular location, the profile image being apicture or short video of the user; determining if the location datafrom the first user system and the second user system is within a venue;facilitating an in-person communication between two users at anexclusion of an initial spontaneous electronic communication by:providing a notification to the first user system of at least one ofpersonal data and location data of the user of the second user system,without electronic contact information to facilitate electronicconversations between the first user system and the second user systemprior to the in-person communication; providing a canned request toengage in an in-person communication to the first user system responsiveto the first user system and the second user system being within avenue; receiving confirmation from the first user system of the cannedrequest to engage in the in-person communication for the potentialencounter; receiving confirmation from at least one of the first usersystem and the second user system of a human-to-human interactionbetween users of the first user system and the second user system; and,providing electronic contact information for the users subsequent toreceiving confirmation of the human-to-human interaction.
 14. Theautomated method of claim 13, further comprising displaying a listing ofpotential encounters to the first user system, each potential encounterlocated within the venue.
 15. The automated method of claim 13, furthercomprising filtering the listing of potential encounters by using jobtitle.
 16. The automated method of claim 13, further comprisingrequesting profile images from the first user system at pre-determinedgeographic intervals.
 17. An automated system for facilitatinghuman-to-human interaction, comprising: at least one processor executingan encounter software application facilitating an in-personcommunication between two users at an exclusion of an initialspontaneous electronic communication by receiving: determining if firstand second user systems are within a pre-determined geographic areausing location data; receiving a request from the first user system tosend a canned request to the second user system, the canned requestbeing one or more signals indicative of a message lacking in freshnessand spontaneity to engage in an in-person communication, the cannedrequest being configured to be accepted or rejected; displaying themessage of the canned request on the second output device of the seconduser system; confirmation of a request to meet from a first user system,the first user system being a first wireless network-capable mobiledevice; receiving confirmation of the canned request to meet in personfrom the second user system, the second user system being a differentwireless network-capable mobile device than the first user system;receiving confirmation of a human-to-human interaction between users ofthe first user system and the second user system; and, at least onedatabase storing electronic contact information for users of the firstuser system and the second user system; wherein the encounter softwareapplication executed by the processor provides a notification of atleast one of personal identification of each user of the first usersystem and the second user system, or location data of at least one ofthe first user system and the second user system, excluding theelectronic contact information, to facilitate the in-personcommunication prior to confirmation of the human-to-human interactionbetween users of the first user system and the second user system; andwherein at least one of the first user system, and the second usersystem is requested to upload a different profile image when at leastone or more of the following occurs: location data changes; after apre-determined amount of time; when arriving at a particular location; auser of the first user system logging into the encounter softwareapplication, a user of the second user system logging into the encountersoftware application; upon arrival at a new location; or after apredetermined amount of time at a particular location, the profile imagebeing a picture or short video of the user.
 18. The automated system ofclaim 17, wherein the encounter software application executed by theprocessor provides electronic contact information for each user to thefirst user system and the second user system subsequent to confirmationof the human-to-human interaction between users of the first user systemand the second user system.